As far as we know, ramBunctious doesn't trounce around doing skanky things. There are, however, some conflicts with existing products.

Macintosh Easy Open
One of ramBunctious's newer features is the Startup Items folder support. If the startup items are launched, and the desktop is being rebuilt simultaneously, the computer can crash and the RAM disk may become corrupted. This scenario can happen on systems earlier than Mac OS 7.5.2 when Macintosh Easy Open is installed -- Macintosh Easy Open basically forces the desktop to be rebuilt. Therefore, ramBunctious avoids the problem. The Startup Items are not automatically launched if it is an early system and Macintosh Easy Open is installed.

MountImage
MountImage causes problems with several installers and other programs that need to eject disks. ramBunctious needs to unmount RAM disks, and MountImage interferes with that unmounting process. In fact, the author of MountImage has announced that he no longer supports MountImage. ramBunctious detects MountImage and refuses to run if MountImage is installed. ShrinkWrap is an elegant replacement for MountImage; it handles everything MountImage does without conflicting with other applications.

LanRover
The LanRover extension seems to behave poorly with any application that uses temporary memory (also known as MultiFinder memory, or the "Process Manager heap"); since ramBunctious uses temporary memory for the RAM disks, the LanRover extension often conflicts with ramBunctious. This behavior has been seen with LanRover version 3.7.3.

File Sharing
Sometimes it seems impossible to unmount a RAM disk; ramBunctious repeatedly claims that files are open even though you know you've closed all the files. This is usually because of file sharing. Shut down file sharing, and you should be able to unmount the RAM disk. This is the same phenomenon occasionally seen when trying to eject a CD that's being shared.

RAM Doubler
ramBunctious will run perfectly when RAM Doubler is also running, but we found a strange corner case where they didn't get along well. We have worked around that case for RAM Doubler versions up to 1.6.2.

In case you're curious about the corner case we found, it has to do with forcibly exiting the application. Under normal circumstances, the application is stopped by using the "Quit" menu item or a 'quit' Apple Event. It can be forcibly exited by pressing command-control-escape, or by typing "es" from a low-level debugger such as MacsBug. Before we worked around the problem, it would freeze if it was exited via MacsBug. Note that this issue will never arise unless the user forcibly exits the application -- which is usually an ill-advised maneuver anyway.